Systems and methods for securely submitting comments among users via external messaging applications in a cloud-based platform

ABSTRACT

Systems and methods are disclosed for facilitating secure commenting on content items among collaborators via external messaging applications in a collaborative cloud-based environment. In one embodiment, the system receives a response to a notification associated with a content item from a collaborator via an external messaging application. The response can include a text-based comment associated with the content item and secure message information provided by the notification including a message and a message authentication code. The system then determines a validity of the response. The validity of the response can include verifying the integrity of the message using the message authentication code.

CROSS-REFERENCE TO RELATED APPLICATION

The present application claims priority to and benefit from U.S. Provisional Patent Application Ser. No. 61/668,791 titled “SYSTEMS AND METHODS FOR SPECIFYING USER AND ITEM IDENTIFIERS WITHIN AN EMAIL ADDRESS FOR SECURELY SUBMITTING COMMENTS VIA EMAIL”, filed on Jul. 6, 2012, the content of which is incorporated by reference herein.

BACKGROUND

As electronic and digital content use in enterprise settings and/or other organizational settings has become the preferred mechanism for project, task, and work flow management, so has the need for streamlined collaboration and sharing of digital content and documents. In such collaboration environments, multiple users share, access, and otherwise perform actions or tasks on content and files in shared workspaces. This shared access and collaboration requires high availability of the data (e.g., an unfettered ability to download and upload files) as any number of users may have access to a file at any given time.

Overall, the examples herein of some related systems and their associated limitations are intended to be illustrative and not exclusive. Other limitations of existing or prior systems will become apparent to those of skill in the art upon reading the following.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example diagram of a system having a host server of a cloud service and/or cloud storage accounts with capabilities that enable secure submission of comments via external messaging applications.

FIG. 2 depicts a diagram of a web-based or online collaboration platform deployed in an enterprise or other organizational setting for organizing work items and workspaces, as one example of a hosted cloud service and/or cloud storage accounts with capabilities that enable secure submission of comments via external messaging applications.

FIG. 3 depicts an example diagram of a workspace in a cloud-based, online or web-based collaboration environment accessible by multiple collaborators through various devices authorized to access the work space.

FIG. 4 depicts a block diagram illustrating an example of components in a host server for cloud-based services and storage accounts with capabilities that enable secure submission of comments via external messaging applications.

FIG. 5 depicts a block diagram illustrating an example of components in a notification server for providing real time or near real time notifications of activities that occur in a web-based or online collaboration environment.

FIG. 6 depicts a data flow diagram illustrating an example of secure notification generation by a host server for cloud-based services and storage accounts with capabilities that enable secure submission of comments via external messaging applications.

FIG. 7 depicts a data flow diagram illustrating an example of secure comment processing by a host server for cloud-based services and storage accounts with capabilities that enable secure submission of comments via external messaging applications.

FIG. 8 depicts a flow diagram illustrating an example process for facilitating secure submission of comments to a host server of a cloud service and/or cloud storage accounts via external messaging applications.

FIG. 9 depicts a flow diagram illustrating an example process for receiving a response at a host server of a cloud service and/or cloud storage accounts via external messaging applications and submitting a comment included in the response if the response is valid.

FIG. 10 depicts a flow diagram illustrating an example process for determining whether a response is valid by a host server of a cloud service and/or cloud storage accounts.

FIG. 11 depicts an example electronic mail (email) header including various header fields that can be used to facilitate secure submission of comments via external messaging applications.

FIG. 12 depicts a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.

DETAILED DESCRIPTION

The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of the disclosure. However, in certain instances, well-known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure can be, but not necessarily are, references to the same embodiment; and, such references mean at least one of the embodiments.

Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments.

The terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Certain terms that are used to describe the disclosure are discussed below, or elsewhere in the specification, to provide additional guidance to the practitioner regarding the description of the disclosure. For convenience, certain terms may be highlighted, for example using italics and/or quotation marks. The use of highlighting has no influence on the scope and meaning of a term; the scope and meaning of a term is the same, in the same context, whether or not it is highlighted. It will be appreciated that same thing can be said in more than one way.

Consequently, alternative language and synonyms may be used for any one or more of the terms discussed herein, nor is any special significance to be placed upon whether or not a term is elaborated or discussed herein. Synonyms for certain terms are provided. A recital of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification including examples of any terms discussed herein is illustrative only, and is not intended to further limit the scope and meaning of the disclosure or of any exemplified term. Likewise, the disclosure is not limited to various embodiments given in this specification.

Without intent to limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that titles or subtitles may be used in the examples for convenience of a reader, which in no way should limit the scope of the disclosure. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. In the case of conflict, the present document, including definitions will control.

Collaboration environments can include features or mechanisms that allow users or collaborators to add or submit comments on files and folders (items), and to reply to comments, via email and/or other external messaging applications. For example, a user can receive an email notification associated with a particular content item and respond to the notification with a comment for that content item. Due to permission and privacy settings, however, users are typically only allowed to leave comments on items which they are authorized to view.

Unfortunately, as discussed above, the current mechanisms are not secure. For example, when a notification regarding a particular content item is sent by email, the email header can contain information indicating the particular content item (e.g., content identifier) and/or user (e.g., a user identifier). Therefore, another user that is not otherwise authorized to comment on a particular content item can comment on that content item if the user obtains the appropriate user identifier and/or content item identifier. This information is often contained in and obtainable from an email header.

Embodiments of the present disclosure include systems and methods for securely commenting on content items in a collaborative cloud-based environment via external messaging applications such as, for example, electronic mail (e.g., email or SMS).

FIG. 1 illustrates an example diagram of a system having a host server 100 of a cloud service and/or cloud storage accounts with capabilities that enable secure submission of comments via external messaging applications.

The client devices 102 can be any system and/or device, and/or any combination of devices/systems that is able to establish a connection, including wired, wireless, cellular connections with another device, a server and/or other systems such as host server 100 and/or notification server 150. Client devices 102 will typically include a display and/or other output functionalities to present information and data exchanged between among the devices 102 and/or the host server 100 and/or notification server 150.

For example, the client devices 102 can include mobile, hand held or portable devices or non-portable devices and can be any of, but not limited to, a server desktop, a desktop computer, a computer cluster, or portable devices including, a notebook, a laptop computer, a handheld computer, a palmtop computer, a mobile phone, a cell phone, a smart phone, a PDA, a Blackberry device, a Treo, a handheld tablet (e.g. an iPad, a Galaxy, Xoom Tablet, etc.), a tablet PC, a thin-client, a hand held console, a hand held gaming device or console, an iPhone, and/or any other portable, mobile, hand held devices, etc. running on any platform or any operating system (e.g., Mac-based OS (OS X, iOS, etc.), Windows-based OS (Windows Mobile, Windows 7, etc.), Android, Blackberry OS, Embedded Linux platforms, Palm OS, Symbian platform. In one embodiment, the client devices 102, host server 100, and app server 110 are coupled via a network 106. In some embodiments, the devices 102 and host server 100 may be directly connected to one another.

The input mechanism on client devices 102 can include touch screen keypad (including single touch, multi-touch, gesture sensing in 2D or 3D, etc.), a physical keypad, a mouse, a pointer, a track pad, motion detector (e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.), a light sensor, capacitance sensor, resistance sensor, temperature sensor, proximity sensor, a piezoelectric device, device orientation detector (e.g., electronic compass, tilt sensor, rotation sensor, gyroscope, accelerometer), or a combination or variation of the above.

Signals received or detected indicating user activity at client devices 102 through one or more of the above input mechanism, or others, can be used in the disclosed technology by various users or collaborators (e.g., collaborators 108) for accessing, through network 106, a web-based collaboration environment or online collaboration platform (e.g., hosted by the host server 100).

The collaboration platform or environment hosts workspaces with work items that one or more users can access (e.g., view, edit, update, revise, comment, download, preview, tag, or otherwise manipulate, etc.). A work item can generally include any type of digital or electronic content that can be viewed or accessed via an electronic device (e.g., device 102). The digital content can include .pdf files, .doc, slides (e.g., Powerpoint slides), images, audio files, multimedia content, web pages, blogs, etc. A workspace can generally refer to any grouping of a set of digital content in the collaboration platform. The grouping can be created, identified, or specified by a user or through other means. This user may be a creator user or administrative user, for example.

In general, a workspace can be associated with a set of users or collaborators (e.g., collaborators 108) which have access to the content included therein. The levels of access (e.g., based on permissions or rules) of each user or collaborator to access the content in a given workspace may be the same or may vary among the users. Each user may have their own set of access rights to every piece of content in the workspace, or each user may be different access rights to different pieces of content. Access rights may be specified by a user associated with a work space and/or a user who created/uploaded a particular piece of content to the workspace, or any other designated user or collaborator.

In general, the collaboration platform allows multiple users or collaborators to access or collaborate efforts on work items such each user can see, remotely, edits, revisions, comments, or annotations being made to specific work items through their own user devices. For example, a user can upload a document to a work space for other users to access (e.g., for viewing, editing, commenting, signing-off, or otherwise manipulating). The user can login to the online platform and upload the document (or any other type of work item) to an existing work space or to a new work space. The document can be shared with existing users or collaborators in a work space.

A diagrammatic illustration of the online collaboration environment and the relationships between workspaces and users/collaborators are illustrated with further reference to the example of FIG. 2. A diagrammatic illustration of a workspace having multiple work items with which collaborators can access through multiple devices is illustrated with further reference to the example of FIG. 3.

In one embodiment, client devices 102 communicate with the host server 100 and/or people search engine 150 over network 106. In general, network 106, over which the client devices 102, the host server 100, and/or people search engine 150 communicate, may be a cellular network, a telephonic network, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet, or any combination thereof. For example, the Internet can provide file transfer, remote log in, email, news, RSS, cloud-based services, instant messaging, visual voicemail, push mail, VoIP, and other services through any known or convenient protocol, such as, but is not limited to the TCP/IP protocol, Open System Interconnections (OSI), FTP, UPnP, iSCSI, NSF, ISDN, PDH, RS-232, SDH, SONET, etc.

The network 106 can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the client devices 102 and the host server 100 and may appear as one or more networks to the serviced systems and devices. In one embodiment, communications to and from the client devices 102 can be achieved by, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet. In one embodiment, communications can be achieved by a secure communications protocol, such as secure sockets layer (SSL), or transport layer security (TLS).

In addition, communications can be achieved via one or more networks, such as, but are not limited to, one or more of WiMax, a Local Area Network (LAN), Wireless Local Area Network (WLAN), a Personal area network (PAN), a Campus area network (CAN), a Metropolitan area network (MAN), a Wide area network (WAN), a Wireless wide area network (WWAN), enabled with technologies such as, by way of example, Global System for Mobile Communications (GSM), Personal Communications Service (PCS), Digital Advanced Mobile Phone Service (D-Amps), Bluetooth, Wi-Fi, Fixed Wireless Data, 2G, 2.5G, 3G, 4G, IMT-Advanced, pre-4G, 3G LTE, 3GPP LTE, LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks, enhanced data rates for GSM evolution (EDGE), General packet radio service (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, UMTS-TDD, 1×RTT, EV-DO, messaging protocols such as, TCP/IP, SMS, MMS, extensible messaging and presence protocol (XMPP), real time messaging protocol (RTMP), instant messaging and presence protocol (IMPP), instant messaging, USSD, IRC, or any other wireless data networks or messaging protocols.

In one embodiment, actions performed on work items or other activities that occur in a workspace can be detected in real time or in near real time. The host server can generate notifications or notification events for one or more of the plurality of activities and select one or more recipients for each notification. Various mechanisms or external messaging applications can then be used to notify users or collaborators, including through the web interface to access the collaboration platform, via email, and/or SMS, for example.

FIG. 2 depicts a diagram of a web-based or online collaboration platform deployed in an enterprise or other organizational setting 250 for organizing work items 215, 235, 255 and workspaces 205, 225, 245, as one example of a hosted cloud file sharing, collaboration service and/or cloud storage service with capabilities that enable secure submission of comments via external messaging applications.

The web-based platform for collaborating on projects or jointly working on documents can be used by individual users and shared among collaborators. In addition, the collaboration platform can be deployed in an organized setting including but not limited to, a company (e.g., an enterprise setting), a department in a company, an academic institution, a department in an academic institution, a class or course setting, or any other types of organizations or organized setting.

When deployed in an organizational setting, multiple workspaces (e.g., workspace A-N) may be created to support different projects or a variety of work flows. Each workspace may have its own associate work items. For example, work space A 205 may be associated with work items 215, work space B 225 may be associated with work items 235, and work space N may be associated with work items 255. The work items 215, 235, and 255 may be unique to each work space but need not be. For example, a particular word document may be associated with only one work space (e.g., work space A 205) or it may be associated with multiple work spaces (e.g., Work space A 205 and work space B 225, etc.).

In general, each work space has a set of users or collaborators associated with it. For example, work space A 205 is associated with multiple users or collaborators 206. In some instances, work spaces deployed in an enterprise may be department specific. For example, work space B may be associated with department 210 and some users shown as example user A 208 and workspace N 245 may be associated with departments 212 and 216 and users shown as example user B 214.

Each user associated with a work space may generally access the work items associated with the work space. The level of access may depend on permissions associated with the specific work space, and/or with a specific work item. Permissions may be set for the work space or set individually on a per work item basis. For example, the creator of a work space (e.g., one of user A 208 who creates work space B) may set one permission setting applicable to all work items 235 for other associated users and/or users associated with the affiliate department 210, for example. Creator user A 208 may also set different permission settings for each work item, which may be the same for different users, or varying for different users.

In each work space A, B, . . . , N, when an action is performed on a work item by a given user or any other activity is detected in the work space, other users in the same work space may be notified (e.g., in real time or in near real time, or not in real time). Activities which trigger real time notifications can include, by way of example but not limitation, adding, deleting, or modifying collaborators in the work space, uploading, downloading, adding, deleting a work item in the work space, creating a discussion topic in the work space.

Specifically, items or content (content items) downloaded or edited in accordance with the techniques described in the present disclosure can cause notifications to be generated. Such notifications can be sent to relevant users to notify them of actions surrounding a download, an edit, a change, a modification, a new file, a conflicting version, an upload of an edited or modified file.

In one embodiment, in a user interface of the web-based collaboration platform where notifications are presented, users can, via the user interface, create action items (e.g., tasks) and delegate the action items to other users including collaborators pertaining to a work item 215, for example. The collaborators 206 may be in the same workspace A 205 or the user may include a newly invited collaborator. Similarly, in the same user interface where discussion topics can be created in a work space (e.g., work space A, B or N, etc.), actionable events on work items can be created and/or delegated/assigned to other users such as collaborators of a given work space 206 or other users. Through the same user interface, task status and updates from multiple users or collaborators can be indicated and reflected. In some instances, the users can perform the tasks (e.g., review or approve or reject, etc.) via the same user interface.

FIG. 3 depicts an example diagram of a workspace 302 in an online or web-based collaboration environment accessible by multiple collaborators 322 through various devices authorized to access the work space.

Each of users 316, 318, and 320 may individually use multiple different devices to access and/or manipulate work items 324 (e.g., content items) in the work space 302 with which they are associated with. For example users 316, 318, 320 may be collaborators on a project to which work items 324 are relevant. Since the work items 324 are hosted by the collaboration environment (e.g., a cloud-based environment), each user may access the work items 324 anytime, and from any physical location using any device (e.g., including devices they own or any shared/public/loaner device).

Work items to be edited or viewed may be accessed from the workspace 302 in accordance with the platform and/or application independent mechanisms. Users may also be notified of access, edit, modification, and/or upload related-actions performed on work items 324 by other users or any other types of activities detected in the work space 302. For example, if user 316 modifies a document, one or both of the other collaborators 318 and 320 can be notified of the modification in real time, or near real-time, or not in real time. The notifications can be sent through any of all of the devices associated with a given user, in various formats including, one or more of, email, SMS, or via a pop-up window in a user interface in which the user uses to access the collaboration platform. In the event of multiple notifications, each notification may be depicted preferentially (e.g., ordering in the user interface) based on user preferences and/or relevance to the user (e.g., implicit or explicit).

For example, a notification of a download, access, read, write, edit, or upload related activities may be presented in a feed stream among other notifications through a user interface on the user device according to relevancy to the user determined based on current or recent activity of the user in the web-based collaboration environment.

In one embodiment, a notification feed stream includes updates when an invited user accepts an invitation and/or successfully creates a new account through receipt of an invitation from an existing user. The invited user, upon creation of the new account, receives the account having enhanced features. The new user can automatically be connected to the existing user who sent the invitation. The system can also automatically prompt both users to query they wish to be collaborators in a common work space.

Work items hosted by a collaboration environment (e.g., a cloud-based collaboration environment) can be accessed by users (e.g., users 316, 318, and 320) via multiple different devices (e.g., devices 304-314) for viewing, editing, processing or performing other manipulations on work items. The devices can include applications for accessing a server hosting a cloud-based platform or service or other backend web services (hereinafter “cloud-based collaboration platform application”) and applications for viewing, editing, processing, or performing other manipulations on work items. The communication between such applications are generally facilitated by a communication mechanism of the OS. For example, in Android OS, the communication mechanism is based on “Intents”. As previously described, the underlying communication mechanism are generally insecure, and any data passed between applications are visible to all other application on a device.

FIG. 4 depicts a block diagram illustrating an example of components in a host server 400 for cloud-based services and storage accounts with capabilities that enable secure submission of comments via external messaging applications. The host server 400 can be host server 100 of FIG. 1 although alternative configurations are possible.

The host server 400 of the web-based or online collaboration environment can generally be a cloud-based service. The host server 400 can include, for example, a network interface 402, an activity detector 405, a secure comment manager 420, a notification engine 415, and a permissions manager 435. The notification engine 415 can include a notification server manager 416 and a recipient selection module 417. The permission manager 435 can include a workspace manager 436, a collaboration manager 438, an organization tracker 440 having an enterprise tracker 441, and a work item manager 442. Additional or fewer components/modules/engines can be included in the host server 400 and each illustrated component. Further, although illustrated as included as part of the host server 400, the components/modules/engines can be physically and/or functionally distributed.

The network interface 402 can be a networking module that enables the host server 400 to mediate data in a network with an entity that is external to the host server 100, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface 402 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.), Bluetooth, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.

As used herein, a “module,” “a manager,” a “handler,” a “detector,” an “interface,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, hander, or engine can be centralized or its functionality distributed. The module, manager, hander, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor. As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.

One embodiment of the host server 400 includes the activity detector 405 which can detect an activity in the web-based collaboration environment. The activity can be a triggering activity which causes a notification to be generated and/or added to one or more queues associated with selected or relevant users so that those selected or relevant users are notified of the occurrence of the activity in real-time or near real time and/or in a batched notification at a later time.

The detected activity can be performed by a user or collaborator in a workspace and can be performed on a work item or relating to a work item, for example, download or upload of the work item, previewing, commenting of a work item, deletion or editing of the work item, commenting on a work item, identifying, selecting, adding, deleting, saving, editing, and modifying a tag in the work item, setting or changing permissions of the work item, sharing the work item including, for example, emailing a link to the work item, embedding a link to the work item on another website. The types of activities that can be detected can also relate to changes to a workspace, such as adding, deleting, or modifying collaborators in the workspace; changes to work items such as adding, deleting a work item in the workspace; creating a discussion topic in the workspace, adding a response to a discussion topic, deleting a response, or editing a response in the workspace.

Detected activity in a workspace that is performed by a user or otherwise occurring can trigger notifications to be generated and sent out in real-time or near real-time and/or subsequently sent out via a batched notifications at later times via, for example, the notification engine 415. The notification engine 415 can notify users, which can be collaborators with the user who performed the activity in the workspace, via one or more of many mechanisms, including but not limited to, email, SMS, voice-message, text-based message, RSS, feed, etc. The mechanisms can be configurable by each user or collaborator based on the type of activity that occurred and/or where the activity occurred in the workspace (e.g., which storage container or folder in the workspace).

In one embodiment, the notification is depicted through a web-browser to another user in the web-based collaboration environment. In some embodiments, the notification can be depicted in real-time or near real-time to the time in which the activity was performed by the user and/or at some later time in a batched notification with other notifications that are to be depicted to the user. When notifying a user in real-time or through the use of a batched notification using a web-browser, the notification engine 415 can utilize a push-enabled service. In one embodiment, the real-time or batched notifications are sent by a component or another server which implements push technology (e.g., the notification server 500 shown in the example of FIG. 5). The push-enabled service can be implemented via long poll or HTTP streaming, for example, by the notification server 500 or another component, device which may be internal to or external to the host server 400. In addition, the host server 400 could utilize other push servers including third party push servers to implement push technology including but not limited to mobile platform push systems and services (e.g., via smart phones or tablets or other portable devices such as iPhone, Android phones, Blackberry, iPad, Galaxy or other tablets, etc.).

The host server 400 can send a notification server an identification of the recipient to be notified and an indicator of the one or more activities to notify the recipient of (e.g., via a batched notification). The indicator of the one or more activities to notify the recipient of can be in the form of a batched notification which comprises one or more notifications that are stored in a queue associated with the recipient. Alternatively or additionally, the host server 400 can send the notification server the address or location or multiple locations of the queue(s) from which to read and send the notifications as a batched notification to the user. Use of an external push server, such as the notification server 550 is described with further reference to the example of FIG. 5.

The notification server 550 can be managed by the notification server manager 416 in the notification engine 415 which can communicate events to notify users in real-time via their browser interfaces or queue up notifications to send users batched notifications. In one embodiment, the host server sends a notification server an identification of the recipient to be notified and/or an indicator of the one or more activities to notify the recipient of (e.g., via a real-time and/or batched notification).

The recipient selection module 417 can select one or more users for each notification event. For example, the selection module 417 can select one or more recipients for each notification or notification event that is generated by the notification generation module 418. The recipients can be selected, for example, according to criteria determined based on a workspace in which the associated activity was performed in the online collaboration environment. The criteria may be determined in a variety of ways. For example, the criteria can be determined based on an affiliation with a workspace or storage container in which the activity was performed in the online collaboration platform, based on an affiliation with the work item on which the activity was performed, based on permissions configured for the workspace, storage container, or work item, and/or based on predetermined settings configured for the workspace, storage container or folder, and/or individual work items. Combinations and/or variations of the criteria are also possible.

One embodiment of the host server 400 includes the secure comment manager 420 which can generate notifications with secure information and process received responses to notifications including comments to determine whether or not to submit the comments. The secure comment manager 420 facilitates submission of secure comments on content items (e.g., files and/or folders).

In one embodiment, the secure comment manager 420 includes the secure notification generation engine 422. The secure notification generation engine 422 is configured to generate a notification including secure information responsive to a trigger (e.g., action requiring notification of one or more users).

In one embodiment, the notification comprises an email including one or more email headers. As shown and discussed in greater detail with reference to FIG. 11, an email can include a Reply-to email header. The secure notifications can be accomplished using the Reply-to email header. The From header is a generic header for the application, but when a user replies within a mail client to an email notification the response can be sent to the address specified in the Reply-to header. For example, a Reply-to header may include an email address “userid.contentid@reply.company.com.” In this example, the prefix is “userid.contentid,” and the domain for that address is “@reply.company.com.” The domain can direct the email to a particular mail server. In one embodiment, reply emails from an “@reply . . . ” domain can be filtered from other domain messages (e.g., “@company.com”).

The Reply-to header is typically not shown (visible to users) by email applications but it can be accessed by users and thus a malicious user could ascertain a user ID and a content ID from an email address prefix and responsively send an email that appears to be a response to the email notification. That is, a malicious user can email a comment on a content item that the malicious user does not have permission to access.

Accordingly, as described herein, a prefix can be modified such that the user ID and the content ID can be extracted by the system but not modified by malicious users. The secure notification generation engine 422 performs this modification process by generating a unique message authentication code (MAC) based on a message (MSG) that can include, for example, the user ID and the content ID. In some embodiments, the MSG can also include a time stamp. The MAC can be generated based on the MSG using, for example, an integrity key (or code) that is kept secret. A deterministic hashing algorithm can be utilized with the integrity key to generate the MAC (i.e., a unique code). Example operation (data flow) of the secure notification generation engine 422 is shown an discussed in greater detail with reference to FIG. 6.

In one embodiment, the secure comment manager 420 includes the secure comment processing engine 424. The secure comment processing engine 424 is configured to process a response including a comment and submit the comment if the response is verified. For example, the secure comment processing engine 424 can parse and/or otherwise extract the MSG from a response and generate.

For example, the secure comment manager 420 can parse a response email into, for example, three parts: the comment, the prefix, and the domain. The prefix is then parsed into the MAC and the MSG. A new MAC can be generated based on the MSG using, for example, the integrity key (or code) that is kept secret. A deterministic hashing algorithm can be utilized with the integrity key to generate the new MAC. Once generated, the new MAC is compared to the received MAC. Consequently, if a malicious user attempts to change the MSG by modifying the user ID and/or the content ID, then the received MAC will not match the new MAC. Example operation (data flow) of the secure comment processing engine 424 is shown an discussed in greater detail with reference to FIG. 7.

In one embodiment, the secure comment manager 420 includes the permissions manager 435. The permissions manager 435 can manage the various user permissions in the in the cloud-based collaboration environment.

In one embodiment, the permissions manager 435 can include the workspace manager 436 which can manage user permissions based on a user's affiliation with a workspace, including, one or more of, member, invited collaborator and collaborator in the workspace. Such user affiliation can be tracked and managed by, for example, the collaboration manger 438.

In one embodiment, the permissions manager 435 can include the organization tracker 440 which tracks and/or manages enterprise associations and affiliations. For example; in some embodiments, enterprises and/or enterprise accounts can specifically be managed, tracked, monitored by the enterprise tracker 441. Permissions for the workspace can be configured by a creator or administrative user of the workspace. The collaboration manager 438 can determine, track, and implement relationships, roles, and/or access levels of multiple users/collaborators. For example, users may be a general user, a creator of the workspace, a creator of a work item, or an administrative user. The permissions for a workspace can be configured by a user, creator, or the administrative user and is generally managed by the collaborations manager 438.

In one embodiment, the permissions manager 435 can include the work item manager 442. Permissions associated with work items can be managed, tracked, updated, revised, or implemented, in one embodiment, by the work item manager 442. For example, the permissions associated with the work item can be set by, a creator of the work item or an administrative user of the workspace. Each workspace can include multiple work items where each of multiple work items has individually configurable permissions. The individually configured permissions can be determined by user roles and rights (e.g., as managed by the collaborations manager 438). The work item manager 442 can communicate with the collaboration manager 438 in setting, configuring, or re-configuring permissions associated with work items.

FIG. 5 depicts a block diagram illustrating an example of components in a notification server 550 for providing real time or near real time notifications of activities that occur in a web-based or online collaboration environment. The notification server 550 generally includes, for example, a push server 505, an SMS notifier 515, and/or a priority module 525. In one embodiment, the push server 505 includes a long poll engine 506 and/or an HTTP streaming engine 508. Additional or less components/modules/engines can be included in the notification server 550 and each illustrated component.

As used herein, a “module,” “a manager,” a “handler,” a “detector,” an “interface,” a “controller,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, handler, or engine can be centralized or its functionality distributed. The module, manager, handler, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor. As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.

The notification server 550 can support the services of a collaboration platform or environment to provide real time (or near real time) and/or batched notifications of activities. In one embodiment, the notification server 550 is integrated within a host server of a collaboration platform (e.g., the host server 100 shown in the example of FIG. 1 or the host server 400 shown in the example of FIG. 4, for example). The notification server 550 may also be externally coupled to the host server (e.g., the host server 100 or 400. In some instances, a portion of the functions implemented and performed by the notification server 550 can be implemented in part or in whole in the host server 100 or 400. For example, some of the components shown to be in the notification server 500 and associated functionalities can in part or in whole reside in the host server 100 or 400.

In one embodiment, the notification server 550 sends a notification of one or more activities that occur within a collaboration platform to a recipient. In some embodiments, the notification is sent by the server 550 such that the recipient is notified in real time (or near real time) to when the activity occurred or when the activity was performed. Alternatively or additionally, the notification can be sent as a batched notification upon expiry of a timer or upon another triggering event. Notification, including real-time notification, can be performed via push technology, for example by the push server 505 through long polls (e.g., via the long poll engine 506) and/or through the HTTP streaming (e.g., via the HTTP streaming engine 508). The notification server 550 can communicate with the host server to determine a recipient or recipients with whom to notify. The notification server 550 can also determine the activity or activities to notify the recipient of, for example through communication with the host server.

In one embodiment, the notification is presented in a feed stream among other notifications through a user interface on the user device according to relevancy to the user determined based on current or recent activity of the user in the web-based collaboration environment.

In one embodiment, the notification server 550 can send notifications to users via SMS (e.g., through the SMS notifier 515). In this instance, the notification server 500 can be coupled to an SMS center which forwards the SMS text message to a mobile device over a cellular network. The notification can be sent via SMS in real time or near real time, or with a delay.

FIG. 6 depicts a data flow diagram 600 illustrating an example of secure notification generation by a host server for cloud-based services and storage accounts with capabilities that enable secure submission of comments via external messaging applications.

To begin, a notification engine 610 receives a notification trigger associated with a particular content item and identifies an appropriate user (or collaborator) to which to send a notification. In the example of FIG. 6, the user is identifiable using user ID 611 and the particular content item is identifiable using a content ID 612. The notification engine 610 sends the user ID 611 and the content ID 612 to a MSG generator 620. Additionally, a timestamp 615 can also be generated to indicate the current time (or the time that the message (MSG) is generated. The timestamp may for example, indicate a date. Alternatively or additionally, the timestamp 615 can be more granular indicating a time of day.

The MSG generator 620 concatenates the user ID 611, the content ID 612, and/or the timestamp 615 into a message 622 which is sent to a MAC generator 630. The MAC generator 630 generates a message authentication code based on the message 622 using a secret integrity key 635. In one embodiment, the MAC generator 630 can generate the message authentication code by applying a deterministic hashing algorithm to the message using the secret integrity key. The deterministic hashing algorithm can be, for example, a keyed-hash message authentication code (HMAC).

The clear text generator 640 receives the message and the message authentication code generated by the MAC generator 630 and combines into a clear text. In one embodiment, the message comprises an email address prefix which is limited to 256 bits of data. In this case, the user ID 611, the content ID 612 and the timestamp 615 can each be represented by 64 bits and the message authentication code also can be represented by 64 bits for a total of 256 bits of data. As described herein, the message refers to the user ID 611, the content ID 612 and the timestamp 615. The clear text generator 640 then provides the message and the message authentication code to the scrambler 650 (or cipher).

The scrambler 650 scrambles the message and message authentication code using a secret encryption key 655. The scrambled data remains the same number of bits as the input (e.g., 256 bits). In one embodiment, the scrambler 650 uses the Advanced Encryption Standard (AES) to encrypt the message. The encrypted message is then provided to the encoder 660 that encodes the data. In one embodiment, the encoder 660 turns the bits into computer-readable text (or characters) that can be used in, for example, emails. Lastly, an external application engine 670 determines the appropriate form (e.g., email) and formats the notification. Although not shown, in some embodiments, the external application engine 670 can also provide various constraints based on the type of notification (e.g., email, SMS, etc.). The notification is then sent to the user (collaborator) identified by the user ID.

FIG. 7 depicts a data flow diagram 700 illustrating an example of secure comment processing by a host server for cloud-based services and storage accounts with capabilities that enable secure submission of comments via external messaging applications.

To begin, a response parsing engine 710 receives a response to a notification 705 from the user (or collaborator). The response includes a text-based comment associated with the content item that the notification indicated and secure message information provided by the notification including a message and a message authentication code. The response parsing engine 710 can extract the secure message information and send the secure message information to a decoder 720. The decoder 720 can decode the secure message information and send the decoded secure message information to a de-scrambler 730 for descrambling using the same secret encryption key 655 that is used to scramble the data.

The de-scrambler 730 outputs the message and the message authentication code to a MAC parsing engine 740. The MAC parsing engine 740 parses out the message and sends the message to the MAC generator 630 for generation of a new message authentication code based on the message using the same secret integrity key 635. The new (or generated message authentication code) is then compared to the received message authentication code by the integrity verification engine 760 to determine the integrity of the message (e.g., to verify that the message has not been tampered with). The integrity verification engine 760 provides an integrity status 761 which can indicate whether or not the integrity check passed. For example, if the generated message authentication code is the same as the received message authentication code then the integrity of the message is verified. Otherwise, the message is not verified.

FIG. 8 depicts a flow diagram illustrating an example process 800 for facilitating secure submission of comments to a host server of a cloud service and/or cloud storage accounts via external messaging applications. Process 800 may be performed by a host server such as, for example, host server 100 of FIG. 1 or host server 400 of FIG. 4.

In process 810, the host server detects activity occurring in an online collaboration environment. For example, as discussed above, in each work space, when an action is performed on a work item (or content item) by a given user or any other activity is detected in the work space, other users in the same work space may be notified (e.g., in real time or in near real time, or not in real time). In process 812, the host server selects one or more recipient for notification.

In process 814, the host server generates a notification with secure information. For example, the secure information included with the notification so that the response can include this same information. The system is able to detect if the information is tampered with resulting in a secure system. This process is shown and described in greater detail with reference to FIG. 6. In process 816, the host server sends the notification via an external messaging application.

In process 818, the host server receives a response to the notification via the external application with the secure information and a comment. In process 820, the host server submits the comment included in the response to the notification if the response is verified. A more detailed example of process 820 is shown and discussed in greater detail with reference to the example of FIG. 9.

FIG. 9 depicts a flow diagram illustrating an example process 900 for receiving a response at a host server of a cloud service and/or cloud storage accounts via external messaging applications and submitting a comment included in the response if the response is valid. Process 800 may be performed by a host server such as, for example, host server 100 of FIG. 1 or host server 400 of FIG. 4.

To begin, at process 910, the host server receives a response to a notification associated with a content item from a collaborator via an external messaging application. For example, the host server can receive a response email in response to an email notification. At process 912, the host server determines the validity of the response. An example of the validity determination is shown and discussed in greater detail with reference to FIG. 10.

At a decision process 914, the host server determines whether the response is valid. If not, the host server optionally notifies the collaborator 916 and ends the process without submitting a comment. Other preventative measures may also be taken if the system believes that an attempt was made to modify a response by a malicious user. Otherwise, at process 918, the host server submits the text-based comment associated with the content item in the cloud-based environment.

FIG. 10 depicts a flow diagram illustrating an example process 1000 for determining whether a response is valid by a host server of a cloud service and/or cloud storage accounts. Process 800 may be performed by a host server such as, for example, host server 100 of FIG. 1 or host server 400 of FIG. 4.

To begin, at process 1012, the host server verifies the integrity of the message using the message authentication code. At decision process 1014, the host server determines if the integrity is verified. If so, the process continues to process 1018. Otherwise, at process 1016, the host server indicates that the integrity check failed.

At process 1018, the host server determines an age of the notification using a time stamp including with the response. At decision process 1020, the host server determines if the age of the notification exceeds a threshold. If so, at process 1022, the host server indicates that the timestamp check failed. Otherwise the process continues to process 1024.

At process 1024, the host server verifies that the collaborator is authorized to comment on the content item. At decision process 1026, if the permission are verified (e.g., the collaborator is authorized to comment on the content item), the process ends successfully with the response validated. Otherwise, at process 1028, the host server indicates that the permission check failed.

FIG. 11 depicts an example electronic mail (email) header 1100 including various header fields that can be used to facilitate secure submission of comments via external messaging applications. As discussed herein, the external messaging application can comprise email and an email header can include various fields (or sub-headers) each having a different meaning as shown in the example of FIG. 11. Other headers (sub-headers) are also possible. Further, the return-path is the same as a reply-to header.

FIG. 12 illustrates a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.

In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.

The machine may be a server computer, a client computer, a personal computer (PC), a user device, a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, an iPad, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, a console, a hand-held console, a (hand-held) gaming device, a music player, any portable, mobile, hand-held device, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.

While the machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technique and innovation.

In general, the routines executed to implement the embodiments of the disclosure, may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure.

Moreover, while embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that the disclosure applies equally regardless of the particular type of machine or computer-readable media used to actually effect the distribution.

Further examples of machine-readable storage media, machine-readable media, or computer-readable (storage) media include, but are not limited to, recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disks, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links.

The network interface device enables the machine 700 to mediate data in a network with an entity that is external to the host server, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface device can include one or more of a network adaptor card, a wireless network interface card, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.

The network interface device can include a firewall which can, in some embodiments, govern and/or manage permission to access/proxy data in a computer network, and track varying levels of trust between different machines and/or applications. The firewall can be any number of modules having any combination of hardware and/or software components able to enforce a predetermined set of access rights between a particular set of machines and applications, machines and machines, and/or applications and applications, for example, to regulate the flow of traffic and resource sharing between these varying entities. The firewall may additionally manage and/or have access to an access control list which details permissions including for example, the access and operation rights of an object by an individual, a machine, and/or an application, and the circumstances under which the permission rights stand.

Other network security functions can be performed or included in the functions of the firewall, can be, for example, but are not limited to, intrusion-prevention, intrusion detection, next-generation firewall, personal firewall, etc. without deviating from the novel art of this disclosure.

Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling of connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.

The above detailed description of embodiments of the disclosure is not intended to be exhaustive or to limit the teachings to the precise form disclosed above. While specific embodiments of, and examples for, the disclosure are described above for illustrative purposes, various equivalent modifications are possible within the scope of the disclosure, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative embodiments may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed in parallel, or may be performed at different times. Further, any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges.

The teachings of the disclosure provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various embodiments described above can be combined to provide further embodiments.

Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the disclosure can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further embodiments of the disclosure.

These and other changes can be made to the disclosure in light of the above Detailed Description. While the above description describes certain embodiments of the disclosure, and describes the best mode contemplated, no matter how detailed the above appears in text, the teachings can be practiced in many ways. Details of the system may vary considerably in its implementation details, while still being encompassed by the subject matter disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the disclosure should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the disclosure with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the disclosure to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the disclosure encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the disclosure under the claims.

While certain aspects of the disclosure are presented below in certain claim forms, the inventors contemplate the various aspects of the disclosure in any number of claim forms. For example, while only one aspect of the disclosure is recited as a means-plus-function claim under 35 U.S.C. §112, ¶6, other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claims intended to be treated under 35 U.S.C. §112, ¶6 will begin with the words “means for”.) Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the disclosure. 

What is claimed is:
 1. A method of facilitating secure commenting on content items among collaborators via external messaging applications in a collaborative cloud-based environment, the method comprising: sending a notification associated with a content item to a collaborator via an external messaging application, wherein the notification includes a message and a message authentication code, the message authentication code generated as a function of the message and to be used to verify the integrity of the message when a response to the notification is received, wherein the message includes one or more of a user identifier associated with the collaborator, an item identifier associated with the content item, or a timestamp; receiving a response to the notification from the collaborator via the external messaging application, wherein the response includes a text-based comment associated with the content item, the message and the message authentication code; and determining a validity of the response by verifying the integrity of the message using the message authentication code by: extracting and decoding a response header from the response, the response header including the message and the message authentication code, descrambling the response header using an encryption key to identify the message and the message authentication code, extracting the message and generating a new message authentication code based on the message using an integrity key, and comparing the message authentication code to the new message authentication code to verify the integrity of the message.
 2. The method of claim 1, further comprising: submitting the text-based comment associated with the content item in the cloud-based environment if the response is valid.
 3. The method of claim 1, wherein the integrity of the message is verified if the new authentication code is the same as the message authentication code.
 4. The method of claim 1, further comprising: receiving a notification trigger; determining a user identifier and a content identifier associated with the notification trigger, wherein the user identifier indicates the collaborator and an the item identifier indicates the content item; generating the message by concatenating the user identifier and the content identifier; and generating the message authentication code based on the message.
 5. The method of claim 4, wherein generating the message authentication code and the new message authentication code based on the message further comprises: accessing a secret integrity key; and applying a deterministic hashing algorithm to the message using the secret integrity key.
 6. The method of claim 5, wherein the deterministic hashing algorithm comprises a keyed-hash message authentication code (HMAC).
 7. The method of claim 1, wherein determining the validity of the response further comprises: accessing permissions associated with the content item; and verifying that the collaborator is authorized to comment on the content item based on the permissions, wherein the response is valid if the collaborator is authorized to comment on the content item.
 8. The method of claim 1, wherein determining the validity of the response further comprises: determining an age of the notification using the timestamp; and verifying that the age of the notification does not exceed a threshold, wherein the response is not valid if the age of the notification exceeds the threshold.
 9. The method of claim 1, wherein the message comprises a user identifier associated with the collaborator and an item identifier associated with the content item.
 10. The method of claim 1, wherein the external messaging application comprises email.
 11. The method of claim 1, wherein the external messaging application comprises SMS.
 12. A non-transitory machine-readable storage medium including executable instructions, which when executed by a processor, causes the processor to facilitate secure commenting on content items among collaborators via external messaging applications in a collaborative cloud-based environment, the instructions comprising: instructions for sending a notification associated with a content item to a collaborator via an external messaging application, wherein the notification includes a message and a message authentication code, the message authentication code generated as a function of the message and to be used to verify the integrity of the message when a response to the notification is received, wherein the message includes one or more of a user identifier associated with the collaborator, an item identifier associated with the content item, or a timestamp; instructions for receiving a response to the notification from the collaborator via the external messaging application, wherein the response includes a text-based comment associated with the content item, the message and the message authentication code; and instructions for determining a validity of the response, wherein determining the validity of the response includes verifying the integrity of the message using the message authentication code by: extracting and decoding a response header from the response, the response header including the message and the message authentication code, descrambling the response header using an encryption key to identify the message and the message authentication code, extracting the message and generating a new message authentication code based on the message using an integrity key, and instructions for comparing the message authentication code to the new message authentication code to verify the integrity of the message.
 13. The non-transitory machine-readable storage medium of claim 12, further comprising: instructions for submitting the text-based comment associated with the content item in the cloud-based environment if the response is valid.
 14. The non-transitory machine-readable storage medium of claim 12, wherein the integrity of the message is verified if the new authentication code is the same as the message authentication code.
 15. The non-transitory machine-readable storage medium of claim 12, wherein the instructions for sending the notification include: instructions for generating the notification associated with the content item responsive to a notification trigger; and instructions for sending the notification to the collaborator via the external messaging application.
 16. The non-transitory machine-readable storage medium of claim 15, further comprising: instructions for receiving the notification trigger; instructions for determining a user identifier and a content identifier associated with the notification trigger, wherein the user identifier indicates the collaborator and an the item identifier indicates the content item; instructions for generating the message by concatenating the user identifier and the content identifier; and instructions for generating the message authentication code using the message.
 17. The non-transitory machine-readable storage medium of claim 16, wherein the instructions for generating the message authentication code or the new message authentication code based on the message further comprise: instructions for accessing a secret integrity key; and instructions for applying a deterministic hashing algorithm to the message using the secret integrity key.
 18. The non-transitory machine-readable storage medium of claim 17, wherein the deterministic hashing algorithm comprises a keyed-hash message authentication code (HMAC).
 19. The non-transitory machine-readable storage medium of claim 12, wherein the instructions for determining the validity of the response further comprise: instructions for accessing permissions associated with the content item; and instructions for verifying that the collaborator is authorized to comment on the content item based on the permissions, wherein the response is valid if the collaborator is authorized to comment on the content item.
 20. The non-transitory machine-readable storage medium of claim 12, wherein the instructions for determining the validity of the response further comprise: instructions for determining an age of the notification using the timestamp; and instructions for verifying that the age of the notification does not exceed a threshold, wherein the response is not valid if the age of the notification exceeds the threshold.
 21. The non-transitory machine-readable storage medium of claim 12, wherein the external messaging application comprises an email or SMS.
 22. A collaboration system for facilitating secure commenting on content items among collaborators via external messaging applications in a collaborative cloud-based environment, the method comprising: a processor; a memory unit having instructions stored thereon which when executed by the processor, causes the collaboration system to: send a notification associated with a content item to a collaborator via an external messaging application, wherein the notification includes a message and a message authentication code, the message authentication code generated as a function of the message and to be used to verify the integrity of the message when a response to the notification is received, wherein the message includes one or more of a user identifier associated with the collaborator, an item identifier associated with the content item, or a timestamp; determine a validity of a response to the notification received from the collaborator via the external messaging application, wherein the response includes a text-based comment associated with the content item and secure message information provided by the notification including the message and the message authentication code; and wherein determining the validity of the response includes verifying the integrity of the message using the message authentication code by: extracting and decoding a response header from the response, the response header including the message and the message authentication code, descrambling the response header using an encryption key to identify the message and the message authentication code, extracting the message and generating a new message authentication code based on the message using an integrity key, and comparing the message authentication code to the new message authentication code to verify the integrity of the message.
 23. The collaboration system of claim 22, wherein the instructions, when executed by the processor, further causes the collaboration system to: submit the text-based comment associated with the content item in the cloud-based environment if the response is valid.
 24. The collaboration system of claim 22, wherein the instructions, when executed by the processor, further causes the collaboration system to: send the notification associated with the content item to the collaborator via the external messaging application, wherein the notification includes the message information including the message and the message authentication code associated with the message.
 25. The collaboration system of claim 22, wherein the instructions, when executed by the processor, further causes the collaboration system to: receive a notification trigger; determine a user identifier and a content identifier associated with the notification trigger, wherein the user identifier indicates the collaborator and an the item identifier indicates the content item; generate the message by concatenating the user identifier and the content identifier; and generate the message authentication code based on the message.
 26. The collaboration system of claim 25, wherein generating the message authentication code and the new message authentication code based on the message further comprises: accessing a secret integrity key; and applying a deterministic hashing algorithm to the message using the secret integrity key.
 27. The collaboration system of claim 26, wherein the deterministic hashing algorithm comprises a keyed-hash message authentication code (HMAC).
 28. A machine-readable non-transitory storage medium including executable instructions, which when executed by a processor, causes the processor to: send a notification associated with a content item to a collaborator via an external messaging application, wherein the notification includes a message and a message authentication code, the message authentication code generated as a function of the message and to be used to verify the integrity of the message when a response to the notification is received, wherein the message includes one or more of a user identifier associated with the collaborator, an item identifier associated with the content item, or a timestamp; determine a validity of a response to the notification associated with the content item received from the collaborator via the external messaging application, wherein the response includes a text-based comment associated with the content item and secure message information provided by the notification including a message and a message authentication code; and wherein determining the validity of the response includes verifying the integrity of the message using the message authentication code by: extracting and decoding a response header from the response, the response header including the message and the message authentication code, descrambling the response header using an encryption key to identify the message and the message authentication code, extracting the message and generating a new message authentication code based on the message using an integrity key, and comparing the message authentication code to the new message authentication code to verify the integrity of the message. 